Presentation: Tweet"Things I wish I'd known before I started with Microservices"
A pragmatic guide
There is no one-size-fits-all approach to building microservices. While a number of common aspirations, goals and techniques have been recognised across different microservices initiatives, the variation in implementation techniques and approaches is substantial. This includes things such as which platform to build the system on, and which tools and frameworks to use. In such a context, essential questions about this architectural style, including whether it is fit for purpose for a particular problem, are more often than not difficult to answer.
Having worked on a number of microservices implementations, large and small, we have recognised recurring patterns and challenges; these we have distilled into a set of pragmatic questions and concerns that developers might face in a similar context. In this presentation we would like to discuss the practical aspects of these questions, illustrated with examples from our own work.
Some of the questions we will be covering include:
Why
- What's the big deal?
- Monoliths: friend or foe?
What
- Does size matter?
- Contracts: do we really need to involve legal?
How
- Things I wish I'd known before I started
- Gotchas and anti-patterns